System and method for managing a rechargeable battery based on historical charging data

ABSTRACT

Rechargeable batteries come in many different shapes and sizes. A rechargeable battery typically contains a group of one or more electrochemical cells. These cells degrade over time and use. Disclosed is a system and method for managing a rechargeable battery based on historical charging data. In one embodiment, the method includes storing a 1 st  timestamp in memory of a mobile information handling system, wherein the 1 st  timestamp identifies a time of day in which a 1 st  cycle for charging a battery started. A 2 nd  timestamp is also stored in the memory, wherein the 2 nd  timestamp identifies a time of day in which a 2 nd  cycle for charging the battery started. Thereafter an integer N based is generated on the 1 st  and 2 nd  timestamps, wherein N defines a recommended number of consecutive day(s) for charging the battery.

BACKGROUND OF THE INVENTION

An information handling system processes, compiles, stores, and/orcommunicates information for business, personal, or other purposes.Technology and information handling needs and requirements can varybetween different applications. Thus information handling systems canalso vary regarding what information is handled, how the information ishandled, how much information is processed, stored, or communicated, andhow quickly and efficiently the information can be processed, stored, orcommunicated. The variations in information handling systems allowinformation handling systems to be general or configured for a specificuser or specific use such as financial transaction processing, airlinereservations, enterprise data storage, or global communications. Inaddition, information handling systems can include a variety of hardwareand software resources that can be configured to process, store, andcommunicate information. Information handling systems can also implementvarious virtualized architectures. Data and voice communications amonginformation handling systems can occur via networks that are wired,wireless, or some combination.

SUMMARY

Rechargeable batteries are used in mobile information handling systemssuch as laptop computers. Rechargeable batteries come in many differentshapes and sizes. A rechargeable battery typically contains a group ofone or more electrochemical cells. These cells degrade with time anduse. Disclosed is a system and method for managing a rechargeablebattery in the mobile information handling system based on historicalcharging data and/or discharging data. In one embodiment, the methodincludes storing a 1^(st) timestamp in memory of the mobile informationhandling system wherein the 1^(st) timestamp identifies a time of day inwhich a 1^(st) cycle for charging a battery started. A 2^(nd) timestampis also stored in the memory, wherein the 2^(nd) timestamp identifies atime of day in which a 2^(nd) cycle for charging the battery started.Thereafter an integer N based is generated on the 1^(st) and 2^(nd)timestamps, wherein N defines a recommended number of consecutive day(s)for charging the battery. In another embodiment, the charge level on thebattery is measured at fixed time intervals between charging cycles. Themeasured charge levels can be stored in memory of the mobile informationhandling system along with the 1^(st) and 2^(nd) timestamps. In thisother embodiment, the measured charge levels can processed with the1^(st) and 2^(nd) timestamps, to generate a recommendation for the nextcharging cycle.

BRIEF DESCRIPTION OF THE DRAWINGS

It will be appreciated that for simplicity and clarity of illustration,elements illustrated in the Figures are not necessarily drawn to scale.For example, the dimensions of some elements may be exaggerated relativeto other elements. Embodiments incorporating teachings of the presentdisclosure are shown and described with respect to the drawings herein,in which:

FIG. 1 is a block diagram illustrating an example mobile informationhandling system according to an embodiment of the present disclosure;

FIG. 2 illustrates relevant components of an example rechargeablebattery pack employed in the mobile information handling system of FIG.1;

FIG. 3 is a flow chart illustrating relevant aspects of a methodperformed by an example battery monitoring system shown in FIG. 2;

FIG. 4 is a flow chart illustrating relevant aspects of a methodperformed by an example recommendation engine shown in FIG. 2;

FIG. 5 illustrates a graphical representation of data recorded during abattery monitoring period;

The use of the same reference symbols in different drawings indicatessimilar or identical items.

DETAILED DESCRIPTION

The following description in combination with the Figures is provided toassist in understanding the technology disclosed herein. The descriptionis focused on specific implementations and embodiments of thetechnology, and is provided to assist in understanding the technology.This focus should not be interpreted as a limitation on the scope orapplicability of the technology.

An information handling system may take form in a laptop computersystem, desktop computer system, server computer system, smart phone,data storage system, etc. The present technology will be described withreference to mobile information handling systems (e.g., laptopcomputers), or devices that are powered by internal rechargeable batterypacks. As its name implies, rechargeable battery packs containrechargeable batteries or batteries that can be charged and dischargednumerous times. Rechargeable batteries come in many different shapes andsizes. A rechargeable battery typically contains a group of one or moreelectrochemical cells. Chemicals commonly used in the electrochemicalcells include: lead-acid, nickel cadmium (NiCd), nickel metal hydride(NiMH), lithium ion (Li-ion), and lithium ion polymer (Li-ion). Thepresent technology will be described with reference to rechargeablebattery having one or more lithium-ion cells, it being understood thepresent invention should not be limited thereto.

FIG. 1 illustrates an example embodiment of a mobile informationhandling system 100, which contains a rechargeable battery pack 200 thatprovides mobile power. Mobile information handling system 100 caninclude processing resources for executing machine-executable code, suchas a central processing unit (CPU). The information handling system 100can also include computer-readable memory for storing machine-executablecode or data, such as data related to cycles for charging anddischarging a battery within a rechargeable battery pack 200. Additionalcomponents of the mobile information handling system 100 can include oneor more communications ports for communicating with external devices,and various input and output (I/O) devices, such as a keyboard and avideo display. The mobile information handling system 100 can alsoinclude one or more buses operable to transmit information or databetween the various hardware components.

The mobile information handling system 100 can include devices ormodules that embody one or more of the devices or modules describedabove or below, and operates to perform one or more of the methodsdescribed herein. The mobile information handling system 100 includesone or more processors (e.g., processors 102 and 104), a chipset 110, acomputer-readable 120, a graphics interface 130, a basic input andoutput system/extensible firmware interface (BIOS/EFI) module 140, adisk controller 150, a disk emulator 160, an input/output (I/O)interface 170, and a network interface 180. Processor 102 is connectedto chipset 110 via processor interface 106, and processor 104 isconnected to chipset 110 via processor interface 108. Memory 120 isconnected to chipset 110 via a memory bus 122. Graphics interface 130 isconnected to chipset 110 via a graphics interface 132, and provides avideo display output 136 to a video display 134. In a particularembodiment, the mobile information handling system 100 includes separatememories that are dedicated to each of the processors 102 and 104 viaseparate memory interfaces. An example of the memory 120 includes randomaccess memory (RAM) such as static RAM (SRAM), dynamic RAM (DRAM),non-volatile RAM (NV-RAM), or the like, read only memory (ROM), anothertype of memory, or a combination thereof.

BIOS/EFI module 140, disk controller 150, and I/O interface 170 areconnected to chipset 110 via an I/O channel 112. An example of I/Ochannel 112 includes a Peripheral Component Interconnect (PCI)interface, a PCI-Extended (PCI-X) interface, a high-speed PCI Express(PCIe) interface, another industry standard or proprietary communicationinterface, or a combination thereof. Chipset 110 can also include one ormore other I/O interfaces, including an Industry Standard Architecture(ISA) interface, a Small Computer Serial Interface (SCSI) interface, anInter-Integrated Circuit (I2C) interface, a System Packet Interface(SPI), a Universal Serial Bus (USB), another interface, or a combinationthereof. BIOS/EFI module 140 includes BIOS/EFI code operable to detectresources within mobile information handling system 100, to providedrivers for the resources, initialize the resources, and access theresources.

Disk controller 150 includes a disk interface 152 that connects the diskcontroller 150 to a hard disk drive (HDD) 154, and to disk emulator 160.An example of disk interface 152 includes an Integrated DriveElectronics (IDE) interface, an Advanced Technology Attachment (ATA)such as a parallel ATA (PATA) interface or a serial ATA (SATA)interface, a SCSI interface, a USB interface, a proprietary interface.Disk emulator 160 permits a solid-state drive 164 to be connected tomobile information handling system 100 via an external interface 162. Anexample of external interface 162 includes a USB interface.Alternatively, solid-state drive 164 can be disposed within mobileinformation handling system 100.

I/O interface 170 includes a peripheral interface 172 that connects theI/O interface to an add-on resource 174 and to network interface 180.Peripheral interface 172 can be the same type of interface as I/Ochannel 112, or can be a different type of interface. As such, I/Ointerface 170 extends the capacity of I/O channel 112 when peripheralinterface 172 and the I/O channel are of the same type, and the I/Ointerface translates information from a format suitable to the I/Ochannel to a format suitable to the peripheral channel 172 when they areof a different type. Add-on resource 174 can include a data storagesystem, an additional graphics interface, a network interface card(NIC), a sound/video processing card, another add-on resource, or acombination thereof. Add-on resource 174 can be on a main circuit board,on separate circuit board or add-in card disposed within mobileinformation handling system 100, a device that is external to the mobileinformation handling system, or a combination thereof.

Network interface 180 represents a NIC disposed within the mobileinformation handling system 100, on a main circuit board of the mobileinformation handling system 100, integrated onto another component suchas chipset 110, in another suitable location, or a combination thereof.Network interface device 180 includes network channels 182 and 184 thatprovide interfaces to devices that are external to mobile informationhandling system 100. In a particular embodiment, network channels 182and 184 are of a different type than peripheral channel 172 and networkinterface 180 translates information from a format suitable to theperipheral channel to a format suitable to external devices. An exampleof network channels 182 and 184 includes InfiniBand channels, FibreChannel channels, Gigabit Ethernet channels, proprietary channelarchitectures, or a combination thereof. Network channels 182 and 184can be connected to external network resources (not illustrated). Thenetwork resource can include another mobile information handling system,a data storage system, another network, a grid management system,another suitable resource, or a combination thereof.

Exemplary embodiments may packetize messages or data. The mobileinformation handling system 100 may interface with the communicationsnetwork (such as a local area network, a wide area network, and/or theInternet) via the network interface 180. Messages and data may bepacketized into packets of data according to a packet protocol, such asthe Internet Protocol. The packets of data contain bits or bytes of datadescribing the contents, or payload, of a message. A header of eachpacket of data may contain routing information identifying anorigination address and/or a destination address. There are manydifferent known packet protocols, and the Internet Protocol is widelyused, so no detailed explanation is needed.

Rechargeable batteries have a finite life due to unwanted chemical orphysical changes to, or the loss of, the active materials of which theyare made. Without the unwanted chemical or physical changes,rechargeable batteries could last indefinitely over an infinite numberof charge cycles, wherein the charge cycle is defined as the completecharging of the rechargeable battery. Unfortunately the unwantedchemical or physical changes to the active materials adversely affectthe electrical performance of the rechargeable battery. As a result, anolder battery cannot hold charge for a sustained period of time comparedto a newer battery. From a user's perspective, this means that over timea mobile information handling system that originally operated for 12 to15 hours between charging cycles, may only operate for about 6 to 8hours, or less, between charging cycles.

Understandably, users become frustrated with their mobile informationhandling systems as the internal batteries degrade and lose ability tohold charge. Users could replace older batteries in their mobileinformation handling systems with newer batteries. Replacing a battery,however, is expensive and time-consuming. While battery replacementmight be required eventually, Applicants above have unexpectedlydiscovered that managing the charging cycles based on data collectedduring past charging and/or discharging cycles can extend the usefullife of rechargeable batteries. The historical charging and/ordischarging data can be used to provide charging recommendations thatenhances the operation of rechargeable batteries.

Applicants have unexpectedly discovered that batteries have “memory.”This discovery was made after Applicants recorded charging anddischarging data for a rechargeable battery within a mobile informationhandling system. The battery was charged to 100% capacity each day for anumber of consecutive days. During each daily discharge cycle the mobileinformation handling system ran the same software applications withoutvariation to ensure a consistent battery drain. Table 1 below showsbattery data collected by Applicants during 25 consecutive days ofmonitoring the battery.

Charge Level Start Charge Stop Charge 6:00 10:00 2:00 6:00 10:00 DayCycle Cycle AM AM PM PM PM 1. 11:00 PM  5:30 AM 99% 90% 68% 40% 23% 2.11:00 PM  5:30 AM 100% 92% 73% 42% 19% 3. 11:00 PM  5:30 AM 100% 87% 74%42% 21% 4. 11:00 PM  5:30 AM 99% 90% 64% 36% 12% 5. 11:00 PM  5:30 AM100% 89% 69% 45% 23% 6. 11:00 PM  5:30 AM 100% 94% 67% 39% 11% 7. 11:00PM  5:30 AM 99% 90% 70% 48% 24% 8. 11:00 PM  5:30 AM 99% 92% 74% 42% 13%9. 11:00 PM  5:30 AM 100% 91% 76% 47% 22% 10. 11:00 PM  5:30 AM 99% 89%80% 54% 26% 11. 11:00 PM  5:30 AM 100% 86% 67% 37% 18% 12. 10:30 AM12:00 PM 14% 6% 90% 46% 29% 13. 10:30 AM 12:00 PM 17% 9% 89% 48% 31% 14.10:30 AM 12:00 PM 24% 15% 90% 54% 36% 15. 10:30 AM 12:00 PM 29% 19% 90%58% 40% 16. 10:30 AM 12:00 PM 40% 21% 92% 66% 51% 17. 10:30 AM 12:00 PM40% 17% 87% 70% 52% 18. 10:30 AM 12:00 PM 42% 16% 89% 70% 50% 19. 10:30AM 12:00 PM 39% 17% 91% 68% 51% 20. 10:30 AM 12:00 PM 37% 18% 90% 71%49% 21. 10:30 AM 12:00 PM 38% 18% 88% 70% 48% 22. 11:00 PM  5:30 AM 100%67% 46% 32% 18% 23. 11:00 PM  5:30 AM 98% 74% 52% 43% 23% 24. 11:00 PM 5:30 AM 99% 81% 75% 46% 21% 25. 11:00 PM  5:30 AM 99% 91% 80% 60% 23%

The collected data includes battery charge levels expressed as apercentage of full capacity. As seen from the table the charge levelswere recorded 5 times during each day. The table also shows thatcharging cycles varied in time and duration. For days 1 through 11(hereinafter the 1^(st) set of days) the battery was charged to fullcapacity between 11:00 PM and 5:30 AM. For days 12 through 21(hereinafter the 2^(nd) set of days) the battery was charged to fullcapacity between 10:30 AM and 12:00 PM. Lastly, for days 22 through 25(hereinafter the 3^(rd) set of days) the rechargeable battery wascharged to full capacity from 11:00 PM to 5:30 AM, which was the sametime and duration for the charging cycle during days 1 through 11.During each of the discharging cycles, the mobile information handlingsystem ran the same software applications without variation so thatenergy drain on the battery was consistent.

Charge levels recorded during the discharge cycles of the 1^(st),2^(nd), and 3^(rd) sets of days revealed unexpected results. In the1^(st) set (i.e. days 1 through 11), the table shows that charge on thebattery decreased on average 28% between 2:00 PM and 6:00 PM. In the2^(nd) set of days, when the charge cycle occurred between 10:30AM-12:00 PM, the data shows charge level decreased significantly between2:00 PM and 6:00 PM on days 12 through 15. In particular, the chargelevel decrease on these days averaged around 38%, which is substantiallymore than the 28% average decrease that was seen during the 1^(st) setof days. However data for the 2^(nd) set of days also shows an averageof 24% charge level decrease for days 16 to 21, a substantially lowerrate when compared to days 12 through 15. The data for the 2^(nd) setalso shows that the discharge pattern eventually reaches a steady statepattern in which there is little variance between 2:00 PM and 6:00 PM.For the 3^(rd) set of days, the charging cycle was returned to 11:00PM-5:30 AM, which was the same charging cycle for the 1^(st) set ofdays. The data for the 3^(rd) set of days shows the charge leveldecreased on average of about 18% from 2:00 PM to 6:00 PM during days 22through 25. It is further noted that the charge percentage at 2:00 PMand 6:00 PM on days 24 and 25 are very similar to the average chargepercentages at 2:00 PM and 6:00 PM for the 1^(st) 11 days. FIG. 5illustrates a graphical representation of the data contained within thetable.

After changing the charging cycle for the 2^(nd) set of days, aconsiderable decrease in charge occurred between 2:00 and 6:00 PM fordays 12 and 13, which indicates the battery attempts to return to itsprevious steady state discharge pattern. After day 13 the battery fallsinto a new and better discharge pattern. This data shows several daysare needed to enable the battery to adapt to a new charging cycle.However at the end of the period for adaptation, there is more chargeavailable to run applications on the mobile information handling system.The graph of FIG. 5 shows the slow increase\adoption that the batterytakes between points A and B and then once again between points C and D.This data shows that an older battery need not be replaced immediately.Rather, by changing the charge/discharge patterns, the useful life of abattery can be extended.

The current technology exploits the unexpected result described above.More particularly, the current technology collects battery chargingand/or discharging data, and uses this data to recommend a chargingcycle time to the user, as will be more fully described below.

As noted with reference to FIG. 1 mobile information handling system 100includes rechargeable battery pack 200 that supplies power to variouscomponents (e.g., processors 102 and 104). With continuing reference toFIG. 1, FIG. 2 shows a more detailed view of rechargeable battery pack200, which includes a rechargeable battery 202 and a battery monitoringsystem 204. The battery monitoring system 204 may take form in amicrocontroller or a system-on-a-chip. For purposes of explanation only,the battery monitoring system 204 is presumed to take form in amicrocontroller that includes a memory for storing instructions, and acentral processing unit that executes the instructions stored in thememory. This enables the battery monitoring system to perform variousfunctions as will be more fully described below. In addition to batterymonitoring system 204 and battery 202, battery pack 200 includes aswitch 206 controlled by battery monitoring system 204, terminals 208, aresistor R, and a thermistor T.

Battery monitoring system 204 can perform several functions. Batterymonitoring system 204 can measure the voltage Vcharge across battery202. Battery monitoring system 204 can measure current I flowing into orout of the battery 202 by measuring the voltage across resistor R.Battery monitoring system 24 can measure the temperature inside thebattery pack 200 by measuring the voltage across thermistor T.

Battery pack 200 can operate in charge mode or a discharge mode. Thecharge mode begins when terminals 208 are electrically coupled to acharger (not shown). During the charge mode a charging voltage Vin isapplied to terminals 208, and battery 202 is charged with current I. Inthe discharge mode current I flows from battery 202 to variouscomponents (e.g., processor 102) via terminals 208. Battery monitoringsystem 204 can determine the mode of operation based upon the polarityof the voltage across resistor R; if the voltage across resistor R ispositive, battery pack 200 is in the charge mode, and if the voltageacross resistor R is negative, the battery pack 200 is in the dischargemode as it supplies current I and Vcharge to terminals 208.

Battery monitoring system 204 measures operational values (e.g.,Vcharge, I and temperature). Battery monitoring system 204 or anothercomponent can use these measured values to calculate the charge level onbattery 202 and to determine the mode of operation (charge or discharge)at any given time. FIG. 3 illustrates a process implemented by batterymonitoring system 204 or another component, such as processor 102, inresponse to executing instructions stored in memory. For the purposes ofexplanation, it will be presumed that the process of FIG. 3 isimplemented by the battery monitoring system 204. The process begins instep 302 when the battery monitoring system 204 detects when battery 202has switched to charging mode. Battery monitoring system 204 can makethis determination based on a change in polarity of voltage acrossresistor R. In step 304 battery monitoring system 204 records the starttime or time when the charge mode was detected in step 304. In oneembodiment, the battery monitoring system 204 maintains an internalclock. Step 304 can be implemented by copying the internal clock time tolocal memory (e.g., RAM) within battery monitoring system 204. The timecopied to memory 210 in step 304, is referred to as the charging cyclestart timestamp. Battery monitoring system 204 in the form ofmicrocontroller, sets and initiates one of its dedicated hardware timersin step 306. The value within the timer increments with time as soon asthe timer is initiated. Battery monitoring system 204 compares the timervalue to a predetermined value. When the timer value equates to thepredetermined value, or is greater than the predetermined value, thetimer expires. In step 310 battery monitoring system 204 checks fortimer expiration. If the timer has expired the process proceeds to step312 where the battery monitoring system 204 measures battery parameterssuch as current I flowing through resistor R, temperature as indicatedby the voltage across thermistor T, and voltage Vcharge across battery202. Battery monitoring system 204 can store these measured parametersin local memory (RAM). Some or all parameters stored in memory (RAM),including parameters previously measured in accordance with step 312,can be used by battery monitoring system 204 or another component tocalculate the charge level on battery 302 as shown in step 314. Thecharge level can be expressed as a percentage of total charge capacityfor battery 202. At step 316 battery monitoring system 204 checks thecalculated charge level against a predetermined value. If the calculatedcharge level is substantially equal to the predetermined value, thebattery is considered fully charged. In an alternative embodimentbattery monitoring system 204 determines that battery 202 is fullycharged when current I flow into battery 202, as measured by the voltageacross resistor R, is below a predetermined threshold, and the voltageVcharge across battery 202 is about another predetermined threshold.When the battery is determined to be fully charged, battery monitoringsystem 204 copies the start timestamp to memory 210, and the processends. It is noted that memory 210 can store several start timestamps,each one of which results from implementation of the process shown inFIG. 3. If the battery is judged not fully charged at step 316, theprocess returns to step 306 with a reset of the timer.

The battery monitoring system 204 can also calculate the charge level onbattery 202 during the discharging cycles at fixed time intervals.Battery monitoring system 204 can make these calculations based on thesame parameters mentioned above, including Vcharge, current I,temperature, etc. In addition to calculating the charge levels at fixedtime intervals, battery monitoring system 204 can store these calculatedlevels in memory 210 along with timestamps when they were calculated.

FIG. 2 shows a recommendation engine 212, which takes form ininstructions executing on at least one of the processors 102 or 104 ofmobile information processing system 100. Recommendation engine 212 hasaccess to memory 210 and can process the data stored therein to generatea recommendation for charging battery 202. FIG. 4 illustrates a processimplemented by recommendation engine 212 for generating a charge cyclerecommendation in accordance with one embodiment of the technology.

Memory 210 holds charge cycle start timestamps stored therein inaccordance with the implementation of the process shown in FIG. 3.Recommendation engine 212 can use these start timestamps, charging cyclestop timestamps and/or battery charge measurements that were recordedbetween charging cycles, to provide a recommendation to the user forcharging battery 202 in a manner that extends the discharge cycle. FIG.4 illustrates an example process implemented by recommendation engine212. In one embodiment, the recommendation engine, including processshown in FIG. 4, takes form in instructions executing on a processor102. The process shown in FIG. 4 begins when the discharge mode isdetected in step 400. To this end, battery monitoring system 204 candetect a change in voltage polarity across resistor R, which indicatesthat current I flows out of battery 202. When this change is detectedbattery monitoring system 204 can generate a signal that is provided tothe recommendation engine 212, which initiates the process shown in FIG.4. Also, when the discharge mode is detected, recommendation engine canstore in memory 210, a charging cycle stop timestamp or the time whenthe charging cycle has stopped and the discharging cycles has started.In one embodiment the stop timestamp is linked to the start timestampmost recently stored in memory 210. Recommendation engine 212 accessesmemory 210 to read several timestamps stored therein. Recommendationengine 212 uses these timestamps to generate a battery charging cyclerecommendation. Recommendation engine 212 can also generate therecommendation based upon discharge levels stored in memory 210.Ultimately, the recommendation includes a recommended start time for thenext charging cycle. This recommendation may identify a number of one ormore consecutive days in which the charge cycle should be started at therecommended start time. This recommendation may also include a time tostop the next charging cycle.

In the embodiment shown in FIG. 4, recommendation engine reads andprocesses the last 2 start timestamps entered into memory 210, it beingunderstood the present invention should not be limited thereto. In otherembodiments, recommendation engine reads and processes the last 3, 4, ormore start timestamps entered into memory 210. The present inventionwill be described with reference to recommendation engine 212 readingand processing the last 2 start timestamps entered into memory 210, itbeing understood the present invention should not be limited thereto.

The recommendation engine 212 compares these 2 start timestamps in step406. The recommendation engine 212 may also process in step 406, thecharge levels stored in memory during discharge cycles. If these 2 starttimestamps are substantially equal to each other (e.g., within 30minutes of each other in one embodiment, less than 60 minutes in anotherembodiment), then recommendation engine 212 generates a message thatrecommends a start time for the next charging cycle. This recommendedstart time should equal the last start timestamp read from memory 210,which corresponds to the most recently completed charging cycle. Ifhowever the last 2 timestamps are not substantially, the recommendationengine generates a message that recommends the next two consecutivecharge cycles start at the same time, which is the time of the laststart timestamp read from memory 210, which corresponds to most to themost recently completed cycle. In an alternative embodiment,recommendation engine 212 can read and compare the last 2 start and stoptimestamp pairs entered into memory 210. If the charging cycles definedby the start and stop timestamp pairs are substantially equal (e.g., 90%time overlap) the recommendation engine 210 generates a message thatrecommends that the next charge cycle start at the time defined by thestart timestamp read from memory 210, which corresponds to the lastcharging cycle. Alternatively, If the charging cycles defined by thestart and stop timestamp pairs are substantially equal (e.g., 90% timeoverlap) the recommendation engine 210 generates a message thatrecommends that the next charge cycle start and stop at the timesdefined by the start and stop times of the last timestamp pair read frommemory 210, which corresponds to the last charging cycle. On the otherhand, if the last 2 timestamp pairs are not substantially equal (e.g.,less than 90 percent time overlap between the pairs), then therecommendation engine 210 generates a message that recommendsconsecutive daily charging cycles, with a start time equal to the timeof the last start timestamp entered into memory 210. Alternatively, ifthe last 2 timestamp pairs are not substantially equal (e.g., less than90 percent time overlap between the pairs), then the recommendationengine 210 generates a message that recommends consecutive dailycharging cycles, with start and stop times equal to the times of thelast pair of timestamps entered into memory 210. Thereafter, the processof FIG. 4 ends.

In one embodiment, recommendation engine 212 can generate the message inthe form of an .xml or .json file. Messages can be stored in memory forsubsequent display on display 134 (see FIG. 1) upon request by the userof the mobile information handling system. FIG. 2 illustrates an examplerecommendation message on display 134.

Battery monitoring system 204 is also capable of interrupting I byopening gate 206 if the user of the mobile information handling systemattempts to start a charge cycle prior to the recommended start timeindicated by the recommendation engine 212 for the next charge cycle.For example, battery monitoring system 204 can open switch 206 inresponse to a command from the recommendation engine if, for example,the user of mobile information handling system 100 attempts to chargebattery 202 prior to the recommended time as. Moreover, batterymonitoring system 204 can open gate 206 if battery monitoring system 204determines that battery 202 has entered an unsafe mode of operation(e.g., the charge level has exceeded a safe limit, the temperature hasexceeded a safe limit, etc.).

The process of FIG. 3, in an alternative embodiment, can be implementedby an information handling system (e.g., a server) in data communicationwith the mobile information handling system 100 via the Internet. Inthis embodiment, information handling system 100 can transmit to theserver the 2 most recently entered charging cycle start and/or stoptimestamps stored in memory 210. The server, which is not shown in thefigures, can process these timestamps to generate a recommendation forthe next charging cycle. The recommendation can be transmitted back tomobile information handling system 100 via the Internet, where it can bedisplayed at the user's request.

While a computer-readable medium is shown to be a single medium, theterm “computer-readable medium” includes a single medium or multiplemedia, such as a centralized or distributed database, and/or associatedcaches and servers that store one or more sets of instructions. The term“computer-readable medium” shall also include any medium that is capableof storing, encoding, or carrying a set of instructions for execution bya processor or that cause a computer system to perform any one or moreof the methods or operations disclosed herein.

In a particular non-limiting, exemplary embodiment, thecomputer-readable medium can include a solid-state memory such as amemory card or other package that houses one or more non-volatileread-only memories. Further, the computer-readable medium can be arandom access memory or other volatile re-writable memory. Additionally,the computer-readable medium can include a magneto-optical or opticalmedium, such as a disk or tapes or other storage device to storeinformation received via carrier wave signals such as a signalcommunicated over a transmission medium. Furthermore, a computerreadable medium can store information received from distributed networkresources such as from a cloud-based environment. A digital fileattachment to an e-mail or other self-contained information archive orset of archives may be considered a distribution medium that isequivalent to a tangible storage medium. Accordingly, the disclosure isconsidered to include any one or more of a computer-readable medium or adistribution medium and other equivalents and successor media, in whichdata or instructions may be stored.

Although the present invention has been described in connection withseveral embodiments, the invention is not intended to be limited to thespecific forms set forth herein. On the contrary, it is intended tocover such alternatives, modifications, and equivalents as can bereasonably included within the scope of the invention as defined by theappended claims.

What is claimed is:
 1. A method comprising: storing a first most recenttimestamp in a memory of a mobile information handling system, whereinthe first most recent timestamp identifies a time of day in which afirst most recently completed charging cycle for charging a batterystarted; storing a second most recent timestamp in the memory, whereinthe second most recent timestamp identifies a time of day in which asecond most recently completed charging cycle for charging the batterystarted; generating an integer N based on the first and second mostrecent timestamps, wherein N defines a recommended number of consecutiveday(s) for charging the battery beginning at the time of day indicatedby the first most recent timestamp.
 2. The method of claim 1 furthercomprising: reading the first and second most recent timestamps from thememory; processing the first and second most recent timestamps read fromthe memory to generate N.
 3. The method of claim 2, further comprisingan act of generating a message that, when displayed, comprises arecommendation for charging the battery N consecutive day(s).
 4. Themethod of claim 3, wherein the recommendation comprises a start time forcharging the battery on each of the N consecutive day(s).
 5. The methodof claim 4, wherein one of the first and second most recent timestampscomprises the start time.
 6. The method of claim 5, wherein processingthe first and second most recent timestamps comprises comparing thefirst and second most recent timestamps, wherein N equals one if thefirst and second most recent timestamps are substantially equal, andwherein N is greater than 1 if the first and second most recenttimestamps are substantially unequal.
 7. The method of claim 1 furthercomprising: storing a third timestamp in the memory, where the thirdtimestamp identifies a time of day in which the first cycle ended;storing a fourth timestamp in the memory, wherein the fourth timestampidentifies a time of day in which the second charge cycle ended.
 8. Themethod of claim 4 further comprising: detecting that current is flowinginto the battery; wherein the first most recent timestamp is stored inthe memory in response to the detecting; detecting that current isflowing out of the battery; measuring charge levels on the battery atfixed time intervals; storing the charge levels in memory; wherein themessage is generated based on the charge levels.
 9. The method of claim1 further comprising: transmitting the first and second most recenttimestamps to an information handling system; wherein the informationhandling system performs the act of generating N; transmitting N to themobile information handling system for storage therein.
 10. The methodof claim 3, wherein the act of generating N is performed on the mobileinformation handling system, and wherein the method further comprisesthe mobile information handling system displaying the generated message.11. A mobile information handling system comprising: a rechargeablebattery; a first memory for storing processor executable instructions; asecond memory for storing data; a processor for executing instructionsstored in the first memory, wherein the processor executes theinstructions stored in the first memory to perform first operationscomprising: storing a first most recent timestamp in the second memory,wherein the first most recent timestamp identifies a time of day inwhich a first most recently completed charging cycle for charging thebattery started; storing a second most recent timestamp in the secondmemory, wherein the second most recent timestamp identifies a time ofday in which a second most recently completed charging cycle forcharging the battery started; generating an integer N based on the firstand second most recent timestamps, wherein N defines a number ofconsecutive day(s) for charging the battery beginning at the time of dayindicated by the first most recent timestamp.
 12. The mobile informationhandling system of claim 11, wherein the first operations furthercomrpise: reading the first and second most recent timestamps from thememory; processing the first and second most recent timestamps read fromthe memory to generate N.
 13. The mobile information handling system ofclaim 12, wherein the first operations further comprise: generating amessage that, when displayed, comprises a recommendation for chargingthe battery N consecutive day(s).
 14. The mobile information handlingsystem of claim 13, wherein the recommendation comprises a start timefor charging the battery on each of the N consecutive day(s).
 15. Themobile information handling system of claim 14, wherein one of the firstand second most recent timestamps comprises the start time.
 16. Themobile information handling system of claim 15, wherein the processingthe first and second most recent timestamps comprises comparing thefirst and second most recent timestamps, wherein N equals one if thefirst and second timestamps are substantially equal, and wherein N isgreater than one if the first and second most recent timestamps aresubstantially unequal.
 17. The mobile information handling system ofclaim 13, wherein the first operations further comprise: storing a thirdtimestamp in the memory, where in the third timestamp identifies a timeof day in which the first cycle ended; storing a fourth timestamp in thememory, wherein the fourth timestamp identifies a time of day in whichthe second charge cycle ended.
 18. The mobile information handlingsystem of claim 13 further comprising: a microcontroller comprising aprocessor, wherein the processor executes the instructions to performsecond operations comprising: detecting that current is flowing into thebattery; wherein the first most recent timestamp is stored in the memoryin response to the detecting; detecting that current is flowing out ofthe battery; measuring charge levels on the battery at fixed timeintervals; storing the charge levels in memory; wherein the message isgenerated based on the charge levels.
 19. A mobile information handlingsystem comprising: a rechargeable battery; means for storing first andsecond most recent timestamps in a memory, wherein the 1^(st) mostrecent timestamp identifies a time of day in which a first most recentlycompleted charging cycle for charging the battery started, and whereinthe second most recent timestamp identifies a time of day in which asecond most recently completed charging cycle for charging the batterystarted; means for generating an integer N based on the first and secondmost recent timestamps, wherein N defines a number of consecutive day(s)for charging the battery beginning at the time of day indicated by thefirst most recent timestamp.
 20. The mobile information handling systemof claim 19 wherein the means for generating comprises a means forcomparing the first and second most recent timestamps, wherein N equalsone if the 1 and second most recent timestamps are substantially equal,and wherein N is greater than 1 if the first and second most recenttimestamps are substantially unequal.